Microsoft Distributed Transaction Coordinator (MSDTC) fails to auto-start. If you run “sc query msdtc” to see the status of MSDTC, the command returns the following output: STATE equals “1 STOPPED” . Cause.

The Microsoft Distributed Transaction Coordinator (MSDTC) service may stop unexpectedly on a computer that is running Windows Server 2012 or Windows Server 2008 R2 Service Pack 1 (SP1).

SQL Server could not register with Microsoft Distributed Transaction Coordinator (MS DTC) as a resource manager for this transaction. The transaction may have been stopped by the client or the resource manager.

Microsoft Distributed Transaction Coordinator (MSDTC) is enabled in SQL Server 2017. Resolution. This improvement is included in the following cumulative update for SQL Server: Cumulative Update 16 for SQL Server 2017

Symptoms. Assume that you use distributed transactions in Microsoft SQL Server together with MS DTC (Distributed Transaction Coordinator). You may sometimes notice lower throughput and long wait times for the DTC_STATE wait type if there are many concurrent distributed transactions.

Assume that you use Distributed Transaction Coordinator (DTC) transactions in SQL Server 2019 with Tempdb Memory-Optimized Metadata mode enabled. In some scenarios, DTC transactions involving tempdb metadata-related operations could fail internally, with an error related to transactions on memory-optimized tables not being supported in DTC ...

Microsoft Distributed Transaction Coordinator (MSDTC) is enabled in SQL Server 2017. Resolution. This improvement is included in the following cumulative update for SQL Server: Cumulative Update 16 for SQL Server 2017. About cumulative updates for SQL Server:

When you enable trace flag (TF) 3924 to clean orphaned Distributed Transaction Coordinator (DTC) transactions in sqlmin!XactMgr::CleanOrphanedXacts, you may notice that an access violation (AV) occurs. Additionally, you may receive a series of dump files. Note TF 3924 is introduced in KB 3145492 to clean up orphaned DTC transactions. Status.

Fixes an issue in which memory corruption occurs during failovers for Distributed Transaction Coordinator (DTC) transactions for the databases in Availability groups (AG) in SQL Server 2017.

When the Trace Flag (TF) 3924 is enabled to clean the orphaned Distributed Transaction Coordinator (DTC) transactions in sqlmin!XactMgr::CleanOrphanedXacts, then an Access violation (AV) occurs. Note A new fix is available in the following KB 4519668 to fix the Access Violation issue.